Fix pet schema validation for name field#225
Open
KrutiChaudhari wants to merge 1 commit intoautomationExamples:mainfrom
Open
Fix pet schema validation for name field#225KrutiChaudhari wants to merge 1 commit intoautomationExamples:mainfrom
KrutiChaudhari wants to merge 1 commit intoautomationExamples:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix schema validation issue for the pet API response.
Changes
nameproperty type in schemas.py from integer to string.Reason
The API returns pet names as strings (e.g., "ranger"), but the schema expected an integer, causing the test_pet_schema test to fail.
Testing
Result
4 tests passed successfully.